Finalize ClawLedger bounty submission with Telegram validation and Solana devnet proof - #1

What changed

• document the real Telegram → ZeroClaw → ClawLedger 200-event checkpoint run
• add fail-closed rolling-trace evidence and post-rotation channel health proof
• tighten the reviewed Skill and daily SOP invocation rules
• expose a Solana devnet Action and local signer that independently decodes the unsigned transaction
• vendor the pinned Solana browser build, eliminating runtime CDN dependence
• add strict finalized-transaction verification and machine-readable public anchor evidence
• include a privacy-safe 2:46 narrated submission demo

Live evidence

A bound Telegram operator drove stock ZeroClaw v0.8.3 to create and independently verify a stable 200-event checkpoint.

• Event count: 200
• Merkle root: df25687ed19a6ec87a4ee025ce8d0d9b03e4809d6257a215865e0f17a4447e29
• Memo: clawledger:v1:df25687ed19a6ec87a4ee025ce8d0d9b03e4809d6257a215865e0f17a4447e29:200
• Independent local verification: valid: true

Finalized Solana devnet proof

The operator reviewed and explicitly approved an exact one-instruction devnet Memo broadcast. ClawLedger's finalized verifier returned valid: true.

• Explorer: https://explorer.solana.com/tx/N3mzTr1YAWw84b2irzd9Cr4cmPd9JHZSmZaUq3PPTr9xYPLfbJZZEqCMP417164U6exTiBA9kjXZ7pf4PHSQviU?cluster=devnet
• Slot: 481112918
• Fee: 5,000 devnet lamports
• Instructions: exactly one account-free Solana Memo
• SOL/token transfers: none
• Account creation: none
• Machine-readable evidence: docs/FINALIZED_ANCHOR.json

Demo

• 2:46 narrated evidence demo: https://github.com/leafwithered/clawledger/blob/agent/telegram-validation/docs/clawledger-demo.mp4
• Live-screen capture runbook: docs/DEMO.md

Validation

• python -m unittest discover -s tests -v — 17 passed
• GitHub Actions Python 3.11 — passed
• GitHub Actions Python 3.14 — passed
• live Solana devnet RPC and unsigned Action smoke test — passed
• official ZeroClaw v0.8.3 Skill install/audit — passed
• clawledger-anchor SOP validation — passed
• independent finalized Memo verification — valid: true
• repository secret-pattern scan — clean

Safety boundary

The public ClawLedger service is T1: it accepts no seed phrase or private key and has no signing code path. It constructs an unsigned transaction and fail-closes unless it contains the expected payer and exactly one account-free Memo instruction. Raw prompts, logs, Telegram identifiers, credentials, and wallet secrets are excluded from the repository and from the chain.

Submission links

• Repository: https://github.com/leafwithered/clawledger
• Demo: https://github.com/leafwithered/clawledger/blob/agent/telegram-validation/docs/clawledger-demo.mp4
• Devnet proof: https://explorer.solana.com/tx/N3mzTr1YAWw84b2irzd9Cr4cmPd9JHZSmZaUq3PPTr9xYPLfbJZZEqCMP417164U6exTiBA9kjXZ7pf4PHSQviU?cluster=devnet